home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d20
/
makearc3.arc
/
MAKEARC.CFG
< prev
next >
Wrap
Text File
|
1990-12-04
|
9KB
|
208 lines
; FYI, MakeArc is a semi-mail-masher and a link between *.MSG-mailers
; and Opus/Bink-style outbound mail makers (like XST, QEcho, etc.)
; Due to the way it processes the control file, you should also be
; able to use it with Domains ala Bink 2.40...weee!... Since you can
; change your outbound directory anywhere in the file, just process
; one domain, change outbounds, process another, and so forth. It was
; written by the guy who writes XBBS, but it has uses with other BBS/
; Mailer packages. Decide for yourself if it might be for you.
;
; These be all the docs as well as a
; Sample MAKEARC.CFG file. Type MAKEARC ? for additional info. This
; sucker is free-for-the-asking (though copyrighted by me), and if source
; code wasn't included in the archive find the SOB who repacked it and
; kick his sorry ass for me--thanks.
;
; The basic philosophy behind creating a MAKEARC control file is to
; progress from a narrow to wide scope. After setting up the normal
; operating parameters (outbound directory, archiver command, your
; address, and so on), start with individual nodes you want to treat
; specially (by special archiving treatment or routing). From there,
; move to any nets you want processed differently. Note that if you've
; already processed a node in that net, it won't be included in a
; net-wide pass (MAKEARC leaves already-bundled (archived) packets
; alone). From there, process any Zones you want to handle specially.
; Finally, process the entire Domain associated with the outbound
; directory (Bink 2.40 style). You can then change outbound directories
; to process a different Domain in the same manner.
;
; Of course, there are a lot of fancy things you can do if you keep in
; mind the sequential manner in which MAKEARC processes this file...
;
; Finally, remember that it's not necessary to use all of the commands
; that MAKEARC makes available. If all you want is to get your messages
; bundled into archives and you only use one domain (you're only in one
; network), you can get by with something as simple as:
;
; OUTBOUND <outbound dir>
; ARCCMD <archiver command>
; ADDRESS <address>
; DOMAIN
; BREAK
;
; You might need to put NETDIR and MSG in there if you want *.MSG
; attaches as well. If you were only concerned with your Zone,
; you could get rid of DOMAIN and BREAK.
;
;
; Now down to some sample stuff. Immediately below is the control
; file I actually use. Some other purely example stuff is below that.
; Notice that for the command DOMAIN no arguments are required but
; are available optionally. Similarly, arguments for ZONE after the
; Zone#: (i.e. ZONE 3:) are optional, and arguments for NET after the
; Zone:Net#/ (i.e. NET 1:380/) are optional. Arguments following an
; address (i.e. 1:380/100) are optional. In cases where they aren't
; given, the defaults established by ALLTYPE and ARCCMD are used.
;
;
;
SCHED NORMAL ; Schedule tag, not needed if only schedule
;
; All of this stuff is uppercase, but case doesn't really matter.
; Anything after a semi-colon is a comment and is ignored.
; Blank lines are okay too. "Trailing" comments should have
; a space before the semicolon for best results. Tabs are okay but yech.
;
;
; Set up these defaults before you start working on your mail.
; You can change them later at any point, but you want to start
; with *something* in there...
;
;
OUTBOUND C:\BT\FIDONET ; Default outbound directory
ARCCMD PKARC -oct -m ; Default archive command (move to archive)
; Note that if you're making *.MSG attaches
; and want to send naked (unarchived) packets,
; you can set this to DON'T_ARCHIVE to skip
; the archiving process altogether (rename
; *.?UT's to *.PKT's and build attach msg).
ADDRESS 1:380/16 ; Your address
ALLTYPE Hold ; Default type of attach
;NETDIR C:\BT\MSG ; Netmail directory (use with MSG below)
;MSG ; <--if you want *.MSG attaches instead of
; flow files (for FD, etc.)
;
;
; Now to the work of making archived bundles from packets and doing
; some routing...
;
;
;ROUTE 1:380/20 ; Route mail to EC through NEC
;1:396/1 Crash PKARC -m ; Note that you don't have to provide the
; ; mail type and archiver command string
; ; for these entries--they override the
; ; defaults you've setup if present.
;
;
;ROUTE 0:0/0 ; Stop routing
;
;
1:380/100 Crash PKZIP -m ; nodes with special handling
1:380/20 Crash PKZIP -m ; "
;
;
NET 1:380/ Crash PKARC -m ; do the rest of net 380
;
;
MOVE 1 2:4177/1 Hold ; Move XBBS Echo to right outbound
MOVE 1 2:281/504 Hold ; WARNING: This is not the same as a gateway!
MOVE 1 6:600/4 Hold ;
;
;
2:4177/1 Hold PKZIP -m ; Another special case
;
;
DOMAIN ; Global pass through *all* zones of default
; domain. A domain is considered to be a 'set'
; of outbound directories (i.e. C:\BT\FIDONET,
; C:\BT\FIDONET.001,...C:\BT\FIDONET.FFF
; This should work with BinkleyTerm 2.40
; You could also say DOMAIN C:\BT\ALTNET
;
;
BREAK ; End of this schedule. END instead of BREAK
; would cause a default global pass through the
; default OUTBOUND area (your default Zone in
; this Domain).
;
SCHED WEIRD_SCHED ; A different schedule tag (fake stuff for demo)
;
OUTBOUND C:\BT\RBBSOUT ; Default outbound directory
ARCCMD PKARC -oct -m ; Default archive command (move to archive)
ADDRESS 8:8/888 ; A different address
CHANGE 8:114/15 Hold ; Change type of mail for an address
POLL 8:380/16 ; Creates a *.CUT header unless a *.CUT exists
ZONE 1 ; Global pass through Zone 1
BREAK ; No global pass though default Zone at end
;
;
SCHED POLLEM ; More fake illustrative garbage
;
OUTBOUND C:\BT\Fidonet
ADDRESS 1:380/16
POLL 1:380/20
BREAK
;
;
; Some hints:
;
; When first debugging, use MAKEARC <configfile> <schedtag> ! | MORE
; which will invoke MAKEARC in Debug mode. You can watch what happens
; a page at a time. MAKEARC <configfile> <schedtag> ? turns More info
; on at startup.
;
; You can quiet down most of MAKEARC's output by using MAKEARC > NUL
;
; It is possible to change your address while MAKEARC is running by
; simply including another ADDRESS statement. Remember that the global
; pass at the end of the run goes through your default outbound (must
; not be one with an extension!), so you'll probably want to use BREAK
; on all secondary address passes.
;
; It's also possible to have a schedule tag within another tag, and thus
; run only part of a schedule at certain times and the full schedule at
; other times.
;
; Finally, MakeArc can use BINKLEY.CFG for a control file. HOLD is a
; doppleganger for OUTBOUND, NETMAIL for NETDIR, and everything else
; should go behind APPLICATION MAKEARC statements. Obviously, this is
; going to slow execution down as MakeArc has to read through all the
; Bink stuff to get to its stuff; but if it floats your boat, go for it.
;
;
; MakeArc was written to be a faster, easier-to-use oMMM replacement.
; Of course, it is probably lacking some features which oMMM has that
; I don't use. Them's the breaks; oMMM is still around. It also lets
; things that make packets work with FD and similarly brain-dead
; mailers. (Just kidding, sorta. I don't like mailers that rely on
; BBS msg base formats. You'd think a mailer would understand the
; transport layer, wouldn't you?) Don't forget to UTSL
; (Use the Source, Luke).
;
; Maybe someday someone will write a real doc file for this thing.
;
;
;
; To fight those nasty notes folks with the initials JD put in their
; QuickBASIC software documentation, remember: Religion--just say NO.
;
;
; M. Kimes
; 1:380/16.0
; (318)222-3455 data
;